I would like to give an outline of how library staff and other Evergreen users can make contributions to the Evergreen codebase at any of the following steps in the process that leads to being made an official Evergreen committer.
Report bugs – how to do it well and get the best outcome
Test patches – how you can get it done even if you don’t administrate your own Evergreen server
Produce code – Even if you don’t think you’re a programmer, some parts of Evergreen are easier to change than you think, such as the Template Toolkit OPAC
Each stage will be further illustrated by stories from prominent Evergreen contributors.